Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Test Compatibility returns true when schema missing #985

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

enismustafaj
Copy link

@enismustafaj enismustafaj commented Oct 30, 2024

To make the api compatible with Confluent Schema Registry, testing the schema compatibility should return "true" whenever the subject, schema or the version is missing

About this change - What it does

References: #479

Why this way

This provides the compatibility with Confluent Schema registry. So, for people switching from Confluent to Karapace it will be a smother transition.

@enismustafaj enismustafaj requested review from a team as code owners October 30, 2024 13:49
Copy link
Contributor

@jjaakola-aiven jjaakola-aiven left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Some ideas for future refactoring, catch the exceptions in the main API func and move the self.r there, just to collect the responses in one place.

@jjaakola-aiven
Copy link
Contributor

@enismustafaj please rebase?

@enismustafaj
Copy link
Author

@enismustafaj please rebase?

@jjaakola-aiven Thank you for having a look. Just rebased.

@enismustafaj
Copy link
Author

@jjaakola-aiven any update on this???

To make the api compatible with Confluent Schema Registry, testing the schema compatibility should return "true" wheneber the subject, schema or the version is missing
@jjaakola-aiven jjaakola-aiven force-pushed the fix/return-compatible-when-schema-not-there branch from e1dddac to 2b218d1 Compare November 27, 2024 06:51
@jjaakola-aiven
Copy link
Contributor

@enismustafaj Sorry, I got caught on other items that required full attention. I rebased the branch, auto-merge should do the magic now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants